home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19950329-19950528
/
000212_news@columbia.edu_Mon Apr 24 01:46:50 1995.msg
< prev
next >
Wrap
Internet Message Format
|
1995-07-31
|
3KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA28930
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Sun, 23 Apr 1995 21:46:54 -0400
Received: by apakabar.cc.columbia.edu id AA15374
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Sun, 23 Apr 1995 21:46:52 -0400
Path: news.columbia.edu!watsun.cc.columbia.edu!jrd
From: jrd@watsun.cc.columbia.edu (Joe R. Doupnik)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: 3.14+hebrew bug? or lynx limitn?
Date: 24 Apr 1995 01:46:50 GMT
Organization: Columbia University
Lines: 39
Message-Id: <3nevua$f0b@apakabar.cc.columbia.edu>
References: <3ndkmr$o4v@nyx10.cs.du.edu>
Nntp-Posting-Host: watsun.cc.columbia.edu
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <3ndkmr$o4v@nyx10.cs.du.edu>,
Gideon Weisz <gweisz@nyx10.cs.du.edu> wrote:
>mskermit with hebrew macro, and vt220, seems to prevent the lynx
>(www reader) from working properly, since it requires arrow keys.
>(neither cursor mode nor application mode helps)
>has *anyone* been able to get their arrow keys to work properly
>with lynx and this combo??
>(i got no answer to my last posting on this subject)
>thanks, gideon
------------------------
I think there is a conspiracy between News agents that causes your
message to appear as a header-only at my place, twice now. Darned computers.
So I'm trying again via Columbia Univ.
Well, let's pull apart the problem. First, the arrow keys do work
ok in MSK. But there are two of each: on the numeric keypad and on the small
"T", and they can be different. To see what each does use command SHOW KEY
and press an interesting key at the resulting prompt. A typical arrow keyboard
verb would be \Klfarr for left arrow. The numeric keypad sends numbers if
NumLock is on, naturally enough. You can redefine what a key sends via the
SET KEY command.
Second, my guess is the remote (it is remote, right?) Lynx program
is thinking of one kind of terminal and Kermit is behaving as another kind.
We have no idea of what that Lynx program is thinking, nor even what kind
of host it's running on. So, it's up to you to diagnose that part. Be sure
it thinks it is talking to a DEC VTxxx terminal of the same kind that MSK
is emulating. If necessary ask the system administrator of the remote
system what kind of terminal Lynx is using and how it can be modified to
match Kermit (and DEC terminals).
Third, we must be careful about high-bit-set bytes traversing the
wire. Some systems chop the bit without telling us, and that makes a mess
of what's sent for many cases (arrow keys included). If the high bit is
chopped somewhere and Kermit is not told about it then use Kermit command
SET PARITY SPACE to inform MSK that there isn't a high bit today.
Joe D.